docs: add ag run hang troubleshooting note#3248
Merged
Merged
Conversation
- README: add fallback note if ag run hangs without creating session - getting-started: add troubleshooting callout pointing to step-by-step setup - Refs #3247 — ag run hangs on first external tester session
Contributor
There was a problem hiding this comment.
Approved — docs-only, all CI green.
Troubleshooting fallback for #3247. 2 files, 4 lines added. Right stopgap until the code fix ships.
OneStepAt4time
added a commit
that referenced
this pull request
May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a troubleshooting note for the
ag runhang that hit our first external tester (broski, #3247).Changes
ag runhangs, use step-by-step setup insteadContext
npx ag run)ag runhang is a code bug (bug: ag run hangs silently — server starts but no session created (first external tester report) #3247), not a docs bug — but users need a fallback until it's fixedRefs #3247